Skip Headers

Oracle® Database Error Messages 10g Release 2 (10.2) Part Number B14219-01 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next

# 58 SQL-01075 to SQL-02157

SQL-01075: you are currently logged on
  Cause: There is already a connection on this host.
  Action: Do not attempt the second connection.

SQL-02100: Out of memory (i.e., could not allocate)
  Cause: SQLLIB was unable to allocate enough memory to execute the program.
  Action: Allocate more memory to the user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02101: Inconsistent cursor cache. Unit cursor/global cursor mismatch
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02102: Inconsistent cursor cache. No global cursor entry.
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02103: Inconsistent cursor cache. Out of range cursor cache reference
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02104: Inconsistent host cache. No cursor cache available
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02105: Inconsistent cursor cache. Global cursor not found
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02106: Inconsistent cursor cache. Invalid Oracle cursor number
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02107: Program too old for runtime library; please re-precompile it
  Cause: The program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.
  Action: Precompile the program with a newer version of the Oracle Precompilers.

SQL-02108: Invalid descriptor passed to run-time library
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02109: Inconsistent host cache. Host reference is out of range
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02110: Inconsistent host cache. Invalid host cache entry type
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02111: Heap consistency error
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02112: SELECT..INTO returns too many rows
  Cause: A SELECT...INTO statement returned more rows than can be stored in the host variable provided.
  Action: There are 3 possible solutions:

  1. Use the precompiler option select_error=no.

  2. Declare a host variable with a larger array dimension.

  3. Declare a cursor or cursor variable for the select statement.

SQL-02113: Unable to open message file
  Cause: SQLLIB was unable to find or open the sqllib message file sql*.msb
  Action: Check that the file exists in the mesg directory and that it is readable

SQL-02114: Invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor
  Cause: An attempt was made to CLOSE a cursor that was already CLOSEd with MODE={ANSI|ANSI14}. A CLOSEd cursor can be re-CLOSEd only when MODE={ORACLE|ANSI13}.
  Action: When MODE={ANSI|ANSI14}, verify that a cursor is not already CLOSEd before trying to CLOSE it. Specify MODE={ORACLE|ANSI13} if a CLOSEd cursor is to be re-CLOSEd.

SQL-02115: Code interpretation problem -- check COMMON_NAME usage
  Cause: With PRO*FORTRAN, this error occurs if the precompiler option COMMON_NAME is specified incorrectly. With other Oracle Precompilers, this error occurs when the precompiler cannot generate a section of code.
  Action: With Pro*FORTRAN, when using COMMON_NAME to precompile two or more source modules, make sure to specify a different common name for each module. With other Oracle Precompilers, if the error persists, call customer support for assistance.

SQL-02116: FATAL ERROR: Reentrant code generator gave invalid context
  Cause: This internal error typically indicates a memory-related error.
  Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

SQL-02117: Invalid SQL Cursor usage: trying to OPEN an OPENed cursor
  Cause: An attempt was made to OPEN a cursor that was already OPENed with MODE={ANSI|ANSI14|ANSI13}. An open cursor can be re-OPENed only when MODE=ORACLE.
  Action: When MODE={ANSI|ANSI14|ANSI13}, verify that a cursor is not already OPENed before trying to OPEN it. Specify MODE=ORACLE if an OPENed cursor is to be re-OPENed.

SQL-02118: Invalid row for a WHERE CURRENT OF operation
  Cause: An attempt was made to reference a nonexistent row using the CURRENT OF clause in an UPDATE or DELETE statement. This happens when no FETCH has been executed or when FETCH returns a "no data found" error that the program fails to trap.
  Action: Check that the last cursor operation succeeded and that the current row of the cursor is valid. The outcome of a cursor operation can be checked in two ways: implicit checking with the WHENEVER statement or explicit checking of SQLCODE in the SQLCA.

SQL-02119: Invalid HSTDEF argument
  Cause: A non-null ptr was given for a hstdef as the second argument to a call to sqlrcn when the first argument was also used. Either the first or the second argument to SQLRCN must be null.
  Action: Pass a null pointer in either the first or second argument to SQLRCN. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlrcn if this error occurs.

SQL-02120: First and second arguments to SQLRCN both null
  Cause: Both the first and second arguments to sqlrcn were null. An HSTDEF must be passed into SQLRCN in either the form of an OCI lda (first argument) or as an HSTDEF pointer itself (second argument).
  Action: Pass in either an OCI LDA or an HSTDEF, but not both. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlrcn if this error occurs.

SQL-02121: Invalid host name
  Cause: The host name passed into a SQLFCN call was not used in a previous call to SQLRCN.
  Action: Use the same identifier used in the corresponding SQLRCN call. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlfcn if this error occurs.

SQL-02122: Invalid OPEN or PREPARE for this database connection
  Cause: An attempt was made to execute an OPEN or a PREPARE statement using a cursor that is currently open for another database connection and, therefore, cannot be used for this connection.
  Action: Close the cursor to make it available for this connection or use a different cursor for this connection.

SQL-02123: Context referenced in EXEC TOOLS GET CONTEXT statement not found
  Cause: The context name given in the EXEC TOOLS GET CONTEXT statement was never stored with an EXEC TOOLS SET CONTEXT statement.
  Action: Use the EXEC TOOLS SET CONTEXT statement to save any contexts to be retrieved later.

SQL-02124: NULL value returned by EXEC TOOLS statement
  Cause: A NULL value was returned by EXEC TOOLS for a host variable that lacks an indicator variable. This error is returned only when MODE=ANSI. When MODE=ORACLE, although the value of the host variable is indeterminate, no error is generated.
  Action: Associate an indicator variable with each host variable to which nulls might be returned.

SQL-02125: Connect error, can't get error text
  Cause: No connection (not even to the default host) was available, so SQLLIB could not get the message text for the Oracle error that occurred. However, SQLLIB returns the Oracle error number, which can be used to look up the message.
  Action: Look up the appropriate message in the Oracle7 Server Messages manual, and follow the Cause and Action information provided.

SQL-02126: Count of array elements cannot be negative (i.e. < 0)
  Cause: The precompiler found a negative number of array elements in the the N or F element of the SQLDA (SQL Descriptor Area, which is used with dynamic SQL Method 4). Before executing the DESCRIBE statement, N must be set to the dimension of the descriptor arrays. After executing the DESCRIBE statement, N must be reset to the actual number of variables DESCRIBEd, which is stored in the F variable.
  Action: Check that the N or F variables are set to non-negative values.

SQL-02127: Precompiler/SQLLIB version mismatch
  Cause: The program was linked to an older version of SQLLIB, which is incompatible with this release of the Oracle Precompilers.
  Action: Relink the program with a newer version of SQLLIB

SQL-02128: Sessions still exist, not logged off
  Cause: A host was not removed ("logged off") from SQLLIB because XA still has sessions associated with that host.
  Action: Before calling SQLXDH to drop a host, XA must either drop all sessions for that host or set the "doit_anyway" flag. *Note: This error *msg* is never actually used. The error *number* is used, given as a possible return value to the sqllib xa function sqlxdh.

SQL-02129: Fetched number of bytes is odd.
  Cause: The program tried to FETCH an invalid column value into a multi-byte NLS host variable. Specifically, the column did not contain valid double-byte data.
  Action: Make sure the column contains only double-byte data. To verify this, use SQL*Plus or Server Manager.

SQL-02130: EXEC TOOLS interface is not available.
  Cause: An attempt was made to link with a version of an Oracle tool that does not support the EXEC TOOLS interface. EXEC TOOLS interface.
  Action: Either upgrade the Oracle tool, or use the EXEC IAF interface.

SQL-02131: Runtime context in use
  Cause: Your application attempted to execute a SQL statement using a runtime context that is already in use.
  Action: Rewrite the application to either wait for one thread to complete before executing another SQL statement with the same runtime context, or to allocate and use a separate runtime context for each thread.

SQL-02132: Unable to allocate runtime context sdfla asdjklfajs jfja ajsdf
  Cause: An attempt to allocate a runtime context failed.
  Action: This error typically occurs when the process memory is low. Allocate more memory and run the application again.

SQL-02133: Unable to initialize process for use with threads
  Cause: This is an internal error.
  Action: Call customer support.

SQL-02134: Invalid runtime context
  Cause: The runtime context associated with this statement has not been properly allocated.
  Action: Rewrite the application to execute the EXEC SQL CONTEXT ALLOCATE statement before executing any SQL statements.

SQL-02135: Unable to initialize date format using supplied mask
  Cause: The runtime library was unable to issue a set date format statement with the date format mask supplied.
  Action: Check the validity of the date format and correct if necessary. Check the ORA error number for further information.

SQL-02136: Invalid NCHAR character set id
  Cause: An attempt was made to bind or define an NCHAR host variable, and the NLS_NCHAR variable was not set correctly.
  Action: Set the NLS_NCHAR environment variable to a valid fixed width character set id and run the application again.

SQL-02137: Multi-threaded agent with no RETURNING clause present
  Cause: The EXEC SQL REGISTER CONNECT statement does not contain a RETURNING clause and the agent is running in threaded mode.
  Action: Re-code the statement to use a RETURNING clause that references a declared sql_context host variable.

SQL-02138: No external procedure context exists
  Cause: The external procedure context passed in the EXEC SQL REGISTER CONNECT statement is not valid.
  Action: Ensure that you have done the following:

  1. Created the PL/SQL procedure/function with a CONTEXT parameter.

  2. Included OCIExtProcContext in the formal parameter list of the external procedure

  3. Correctly passed the OCIExtProcContext to the EXEC SQL REGISTER CONNECT statement.

SQL-02139: Unable to get the OCI handles
  Cause: The call to OCIExtProcGetEnv failed.
  Action: Ensure that the OCIExtProcContext that the external procedure has been created with a CONTEXT parameter and that this context is correctly referenced in the EXEC SQL REGISTER CONNECT statement.

SQL-02140: An unnamed connection already exists
  Cause: An attempt to register an external procedure context was made when an unnamed connection already exists for the runtime context.
  Action: Do not attempt to establish any connections with the EXEC SQL CONNECT statement from external procedures.

SQL-02141: Collection descriptor has not been allocated
  Cause: An unallocated collection descriptor was referenced in a COLLECTION SET or COLLECTION GET statement.
  Action: Allocate the collection descriptor with the EXEC SQL ALLOCATE statement. e.g. EXEC SQL ALLOCATE :coldesc_p;

SQL-02142: Collection is NULL
  Cause: The collection referenced in an EXEC SQL COLLECTION statement is null.
  Action: Check the status of the associated indicator variable prior to executing an EXEC SQL COLLECTION statement.

SQL-02143: Target object has not been properly allocated
  Cause: An attempt was made to retrieve elements from a collection into an unallocated object pointer.
  Action: Allocate the object pointer with the EXEC SQL ALLOCATE statement.

SQL-02144: Invalid ANSI dynamic usage
  Cause: An ANSI allocate, deallocate, get or set descriptor statement was encountered when dynamic option was not set.
  Action: Precompile your source with option dynamic=ansi.

SQL-02145: Invalid dynamic descriptor
  Cause: An attempt to access an unallocated or invalid descriptor was encountered.
  Action: For ANSI descriptors, check that descriptor name is valid and descriptor has been allocated and not previously deallocated. Or if using Oracle descriptors (sqlda) with mode=ansi also use dynamic=oracle.

SQL-02146: Attempt to allocate an existing descriptor
  Cause: An attempt allocated a descriptor which has previously been allocated was encountered.
  Action: Use and unique descriptor name or deallocate the descriptor before attempting to reallocate it.

SQL-02147: ANSI Dynamic occurrence value out of range
  Cause: The value clause in a dynamic GET or SET statement is less than one or greater than MAX given for descriptor allocation.
  Action: Supply a number for the VALUE clause between 1 and the MAX occurrences supplied when the descriptor was allocated.

SQL-02148: ANSI Dynamic count value out of range
  Cause: The count in a dynamic GET or SET statement is less than one or greater than MAX given for descriptor allocation.
  Action: Supply a number for the COUNT clause between 1 and the MAX occurrences supplied when the descriptor was allocated.

SQL-02149: ANSI Dynamic insufficient item descriptor areas
  Cause: The SQL statement being described contains more output items (or columns) than were allocated in the descriptor.
  Action: Increase the MAX number of occurrences when allocating the descriptor.

SQL-02150: Encountered zero length in ANSI dynamic SET statement
  Cause: An invalid length of zero was encountered in an ANSI dynamic statement.
  Action: Set the length to a non-zero value

SQL-02151: Invalid host variable for exact numeric SET statement item
  Cause: An host variable with an invalid type or length was used to get or set an exact numeric item in an ANSI dynamic statement.
  Action: Make sure your host variable is and int or short for C or for COBOL, S9(4) or S9(9) binary/comp/display sign leading separate.

SQL-02152: Invalid numeric variable for use in an array GET/SET statement
  Cause: An host variable with type other than int or short for C or S9(4) or S9(9) binary or comp was used for an exact numeric with and array size > 1.
  Action: Use only int or short for C or S9(4) or S(9) binary or comp for COBOL when supplying an exact numeric in conjunction with the for clause to indicate arrays. Specifically, display sign leading separate is not allowed in this context.

SQL-02153: Invalid character variable for use in a GET/SET statement
  Cause: An host variable with type other than character, string or varchar was found as an item name (other than DATA item) in an ANSI Dynamic GET or SET descriptor statement.
  Action: Host variable types for character items (other than the DATA item) in ANSI dynamic GET or SET descriptor statements must not be of type LONG or LONG VARCHAR. Redeclare the variable to be character, string or varchar type

SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic
  Cause: An ANSI Dynamic SET statement with item name DATA was encountered with out a valid TYPE having been previously set and option mode=ansi was used
  Action: With mode=ansi, you must set the TYPE before setting the DATA. Issue a SET statement with correct item TYPE or, for output issue a DESCRBE to set the item type. Or use mode=oracle which allows the type to default to the type of the bind/define host variable

SQL-02155: Date Time Interval only valid with Dynamic=ANSI
  Cause: An attempt to access the datetime interval code or precision was encountered when type_code option not set to ANSI
  Action: Use precompiler option type_code=ansi to access the date time interval code or date time interval precision

SQL-02156: Invalid type for Indicator or Returned Length
  Cause: A host variable associated with the item Indicator or Returned Length must be of type short or s9(4) comp. If value semantics and scalar they may also be gotten into display sign leading separate host variables
  Action: Use signed short for indicator, ref indicator and returned length, ref returned length host variables in C. For COBOL use s9(4) comp. for GETs only with non-arrays and you may use display sign leading separate host variables

SQL-02157: Source or destination lob is invalid
  Cause: One of the lobs used in the lob append call is invalid or possibly null.
  Action: Make sure the lobs used in the append call are non-null.